Criteria

The feature table must have a primary key constraint consisting of a single numeric or string/character column which will represent the id of the feature. This primary key is required to enable versioning using the standard versioning system of the Oracle Workspace Manager.

The table must have a geometric (SDO_GEOMETRY) column specifying the feature geometry, and this geometry column must be registered in the Oracle Spatial metadata table (ALL_SDO_GEOM_METADATA or the related USER_SDO_GEOM_METADATA view for the user).

The table fields must be of common type (i.e., no user defined type).

The geometry must be all of a similar type (all of the geometries must be a point, line or polygon type, not a mixture of these types). To determine if a table contains more than one geometry type:

SQL>select p.geometry.sdo_gtype, count(*) from your_table p group by p.geometry.sdo_gtype;
GTYPE = 2001 = points
GTYPE = 2002 = lines
GTYPE = 2003 = polygons

Oracle SSO (Single Sign On)

To enable Oracle SSO functionality database administrators must add new Oracle users for each domain account requiring SSO to the target database, prefixed with the string defined by the os_authent_prefix initialization variable (e.g. “OPS$”).

The following SQL script can be modified for this purpose:

CREATE USER "OPS$DOMAIN\USERNAME"  PROFILE "DEFAULT"
  IDENTIFIED EXTERNALLY DEFAULT TABLESPACE "USERS"
  TEMPORARY TABLESPACE "TEMP"
  ACCOUNT UNLOCK;

GRANT UNLIMITED TABLESPACE TO "OPS$DOMAIN\USERNAME" WITH ADMIN OPTION;
GRANT "CONNECT" TO "OPS$DOMAIN\USERNAME" WITH ADMIN OPTION;
GRANT "RESOURCE" TO "OPS$DOMAIN\USERNAME" WITH ADMIN OPTION;

Then make sure that sqlnet.ora (on both database server and database client machines) contains the following line:

SQLNET.AUTHENTICATION_SERVICES = (NTS)

Then when connecting using SQL*Plus where you would normally use “sqlplus user/password@server”, you could then simply use:

sqlplus /@server

Then the database administrator should ensure all required database objects (e.g. tables, indexes, views, sequences etc...) outside of the Oracle SSO user schema have the proper grants so that processes such as "Register Features..." within the "Bentley Geospatial Administrator" application can access them properly.

Workspace Macros

In order to define Oracle SSO for RDBMS properties, within the Bentley Geospatial Administrator the following workspace macros can be added:

Oracle Spatial Connection

To use Oracle SSO when defining a new "Oracle Spatial Connection" choose the "Use Windows Integrated Authentication" option and provide a connection and service name as shown in the following:

Automating Oracle SSO Login

In addition during a Bentley Map session, normal Oracle connection dialogs in the "Interoperability" application can be suppressed by adding an optional MSGEO_USE_ORACLE_SSO environment variable definition to a users workspace in one of the following forms:

Host;Port;Service

MSGEO_USE_ORACLE_SSO = myserver;1521;mydbservice.domain.com

Service Name Only

MSGEO_USE_ORACLE_SSO = mydbservice